Skip to main content
Version: Stage 5 - Deliverable Acceptance Check

Public Review Summary Report

GRID Public Review Summary Report​

The GRID project follows the UN/CEFACT Open Development Process (ODP) - see Project Governance. As such the project has completed a period of public review (stage 4 of the ODP).

This document provides a summary report of the GRID Project Public Review. The controlling record of each comment and how it was processed (including if/how the issue resulted in changes to documentation or design) is maintained within the GitLab environment "issue log". This summary is provided for ease of reference.

The GitLab issues can be found here: https://opensource.unicc.org/un/unece/uncefact/gtr/-/issues

A detailed extract of all the public review related issues has been produced as a stand-alone document: GRID Public Review Detailed Comments

Introduction​

The GRID Project Public Review period was from 22 July 2026 until 21 September 2026. Each review comment was received through one of three channels: email to UN/CEFACT, email to the project email group, and an online form. The review comments were processed as "issues" in the project GitLab respository. The content of each review comment was copied the issue log of the respository ensuring that each comment was accurately represented in the GitLab repository.

A total of 38 Issues were created from the Public Review comments received during this period. This number represents the superset of review comments. Review submissions sometimes contained more than one comment within a single submission. When this occurred the "parent" review comment was entered as an issue and "child" issues raised for each unique comment. This means that a review that contained 5 comments would result in 6 issues: 1 parent and 5 children.

The "#number" references below represent the numbers in the issue log for the project. For example "#112" represents issue 112 and can be found at the following URL: https://opensource.unicc.org/un/unece/uncefact/gtr/-/issues/112

Other issues can be found through the same link construction. For example, issue "#nn" would be found at URL: https://opensource.unicc.org/un/unece/uncefact/gtr/-/issues/nn

Each review comment was then discussed within the project team and a determination reached on how the project should respond to the comment.

The sections below collate the issues into broad themes. The review comment and project team decision is summarised for each issue.

1. Architectural Scope and Governance Boundaries​

The project team received several review comments suggesting an expansion or change to the Global Registrar Information Directory (GRID) scope and purpose beyond its core mandate of identifying authoritative legal registries. While value can be seen in several of these suggestions the general response to these was to refer back to the original brief and scope for the project. In some instances the suggestions provide a potential value add for other parties where the GRID provides a foundational source of data that other services can build on and use.

  • TCPSP and QTSP Eligibility (#112): A request to allow Trust Communication Platform Service Providers (TCPSPs) to be listed as Registrars was rejected. The team clarified that Registrars must hold a legal or statutory mandate as the authoritative source of truth, whereas TCPSPs are consumers of that data at the intermediary layer.

  • Registrar Rating Mechanisms (#89): A proposal to implement a rating system for registries was rejected. The team determined that applying qualitative scores conflicts with UN Member State sovereignty and the binary eligibility assessment model used by GRID.

  • Dispute and Assurance Adjudication (#88, #87): Requests for GRID to track overlapping competence disputes or document underlying registry assurance models (e.g., physical inspection vs. self-declaration) were rejected. These matters remain under the jurisdiction of the UN Member States and their respective legal frameworks.

  • Verifiable Closure vs. Verifiable Credentials (#79): A submission argued that Verifiable Credentials (VCs) fail to establish global trust because material dependencies remain outside the cryptographic proof. The project team rejected structural changes, clarifying that GRID does not claim to "solve for global trust" but provides a transparent, verifiable basis for discovering authoritative registrars. The glossary definition of "verifiable" will be updated to prevent future scope confusion.

  • Delegated Register Operators (#104): A proposal to separate legal accountability from operational responsibility in the schema was rejected to maintain focus on legal accountability. While the separation of responsiblity is understand, the GRID will be a directory of legal authoritative registars. If a GRID registrar delegates operation of the register to another party that is not deemed to change the legal liability unless the UN Member State legislation reflects the delegation. The term "Operator" was updated to "GRID Operator" in the glossary to avoid confusion with national operating delegates.

2. Historical Verification and Credential Lifecycle​

A significant cluster of comments highlighted the need for Relying Parties to verify trade data against historical registry states. These comments drove changes in the proposed implementation and some areas of the documentation.

  • Verifiable History and Temporal Verification (#106, #105, #98, #85, #75, #68): Multiple reviewers requested mechanisms to prove credential validity at past dates, particularly after a key compromise or a Registrar's withdrawal from GRID. The project team accepted these requirements, introducing a normative baseline framework to retain prior verification material (public keys and states) indefinitely so past signatures remain verifiable.

  • Separation of Status Lifecycles (#92): The team agreed to explicitly separate the lifecycles of a Registrar's participation status, its legal mandate, and its cryptographic keys across all GRID schemas and governance documents.

  • Authenticated Directory Snapshots (#93): To support offline verification, the CI/CD pipeline will be extended to package and cryptographically sign snapshot manifests containing version IDs and timestamps.

3. Identity, Authority, and Reliance Limits​

Reviewers requested clearer demarcations between technical cryptographic control, legal organizational identity, and human authority.

  • Key Control vs. Legal Identity (#101): The project team added explicit documentation stating that control of a cryptographic identifier may not, by itself, provide sufficient evidence of legal identity or registration status within a jurisdiction.

  • Authority to Act and Delegation (#108, #77): Requests to include a delegation model within the Digital Identity Anchor (DIA) were rejected. The team clarified that the DIA establishes entity identity, not individual representation or powers of attorney, which remain jurisdiction-specific and outside the DIA's scope.

  • Limits of Directory Inclusion (#99): The Implementation Guidelines were updated to explicitly warn downstream systems that GRID inclusion does not certify product claims, establish product conformity, or prove the physical authenticity of trade items.

  • The "Unverified" Label (#76): Language stating that a non-GRID DIA is "Unverified" was amended to "not verifiable through the GRID" to acknowledge that validity may be established under other legal or trust frameworks.

4. Technical Schema and Implementation Upgrades​

Specific technical adjustments were made to schemas and identifier models to improve implementer clarity.

  • Schema Versioning Strategy (#109): The project adopted a Semantic Versioning (SemVer) framework for schema governance, aligning with the UN Transparency Protocol (UNTP). This ensures backward compatibility for edge node parsers.

  • Registrar-Provisioned Keys vs. Self-Sovereignty (#107): A request to explicitly endorse Registrar-provisioned keys was rejected to prevent the centralization of trade claims. However, guidance was added clarifying that "Applicant-Controlled" keys may be managed by designated Custodial Agents or Wallet Providers.

  • Credential Naming (#100, #74): Proposals to create distinct technical credential types (e.g., "Registrar Trust Credential") were rejected to avoid schema explosion. Instead, documentation prose was updated to differentiate between "GRID-issued DIAs" and "Registrar-issued DIAs".

  • Subdivision Codes (#95): The schema was updated to align with the full ISO 3166-2 format, and explicit null values were made mandatory for omission.

  • Data Quality Tiers (#102): The Implementation Guidelines were updated to harmonize with a consistent three-tier data quality model.

  • JSON Corrections (#96): A case-sensitivity error in the country field example (un_member_state corrected to UN_member_state) was resolved.

5. Parent Submissions and Administrative Actions​

  • Batch Processing (#91, #90, #83, #68): Large, multi-point submissions from RAMIFY OS, the Indian Directorate General of Foreign Trade (DGFT), José Manuel Fernández Núñez, and the TransPacific Trade Nexus (TPTN) were systematically dismantled into standalone child issues to ensure granular processing.

  • Pre-Seeding the Directory (#81): A suggestion to seed the GRID with known government registers was accepted, conditionally limited to entities that have officially confirmed their participation.

  • Administrative Site Prep (#63): Infrastructure was deployed to facilitate the structured intake and processing of these public review comments.